Shareware Super Platinum 8

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Super Platinum 8 / Shareware Super Platinum 8.iso / mac / BACKUP / CDU_V301.ZIP;1 / CDUDOCEN.DOC < prev next >

Wrap

Text File | 1993-07-12 | 96.3 KB | 2,039 lines

…ÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕ ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ∫ CDU CATDISK <tm> ≥ D.I.S.P. ≥ƒƒƒƒø ∫ Utility package ≥ ≥∞∞∞∞≥ «ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ ≥ ≥∞∞∞∞≥ ∫ (c) 1993 Robert W.van Hoeven ≥ Dutch ≥∞∞∞∞≥ «ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ ≥ Independent ≥∞∞∞∞≥ ∫ Release : 3.01 ≥ ShareWare ≥∞∞∞∞≥ ∫ Rel.Date: July, 12th 1993 ≥ Programmer≥∞∞∞∞≥ ÃÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ∞∞∞∞≥ ∫ | ≥∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞∞≥ ∫ ≥ CDC.EXE / CDE.EXE / CDF.EXE | ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ∫ ≥ CDM.EXE / CDR.EXE / CDS.EXE | ⁄ƒƒƒƒƒø | ∫ ≥ CDT.EXE / CDZ.EXE | ≥∞∞∞∞∞≥ | ∫ ≥ | ¿ƒƒ¬ƒƒŸ | ∫ ≥ Lines starting with '≥' are | ⁄ƒƒƒƒ¡ƒƒƒƒø | ∫ ≥ changes to release 2.10/2.11 ------≥≥≥≥≥≥ ÕÕÕ≥------- ∫ ¿ƒƒƒƒƒƒƒƒƒŸ ÃÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕ ∫ Address: Robert W. van Hoeven ∫ PO. Box 131 ∫ 1170 AC Badhoevedorp ∫ Nederland / Holland »ÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕ ≥⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥≥ WARNING : THE FORMAT OF THE CONTROL FILE (THE FORMER CDU.CTL) HAS ≥ ≥≥ BEEN CHANGED TO A *.INI FORMAT. ALL OPTIONS NOW HAVE ≥ ≥≥ DIFFERENT NAMES BUT ONLY THE REALLY CHANGED OR NEW ≥ ≥≥ OPTIONS ARE MARKED AS SUCH. SEE ALSO THE CONVERSION ≥ ≥≥ SCHEME, INCLUDED IN THE CDUTO301.DOC FILE !!!!!!!!!!!!! ≥ ≥¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ WARNING : THIS RELEASE OF CDU WILL ONLY WORK WITH CATDISK <TM> ≥ ≥ RELEASE 7.00 OR HIGHER. IF YOU USE A PRE 6.30 VERSION ≥ ≥ YOU MUST TRY TO FIND THE CDU 1.15 RELEASE AND 6.30 TO ≥ ≥ 6.37 USERS CAN USE THE CDU 2.01 RELEASE !!!!!!!!!!!!! ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 0 ≥ Table of contents ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ 1 ---- General information 1.1 Copyrights and License Agreement 1.2 Newer versions and contacting the author 2 ---- Package description and requirements 2.1 Preface 2.2 Requirements 2.3 History 2.5 Introduction & specs 3 ---- Installation description 3.1 Installation 3.2 The configuration file 3.3 INI options 3.3.1 [General] options 3.3.2 [CDC] options ≥ 3.3.3 [CDE] options 3.3.4 [CDF] options 3.3.5 [CDM] options 3.3.6 [CDR] options 3.3.7 [CDS] options 3.3.8 [CDT] options 3.3.9 [CDZ] options 3.3.10 ['database'] options 4 ---- Runtime information 4.1 General program information 4.2 CDC ≥ 4.3 CDE 4.4 CDF 4.5 CDM 4.6 CDR 4.7 CDS 4.8 CDT 4.9 CDZ 4.10 Notes on tape support 5 ---- Version information and credits 5.1 The BETA-team 5.2 Credits 5.3 Version history 5.4 Copyright, Trademarks ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 1 ≥ General information ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ 1.1 Copyrights and License Agreement ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ - Users of the CDU-package must accept this disclaimer of warranty: - The CDU-package is supplied as is. The author disclaims all warranties, expressed or implied, including, without limitation, the warranties of merchantability and of fitness for any purpose. The author assumes no liability for damages, direct or consequential, which may result from the use of the CDU-package; - The CDU-package is a "shareware program" and is provided at no charge to the user for evaluation. Feel free to share it with your friends, but please do not give it away altered or as part of another system. The essence of "user-supported" software is to provide personal computer users with quality software without high prices, and yet to provide incentive for programmers to continue to develop new products. - If you find this program useful and find that you are using and continue the use of the CDU-package after a 30 days trial period, you must register the CDU-package as described below; - Non-commercial can get a license for the usage up to this release of the CDU-package for a small amount of money. Look into the details in REGISTER.CDU. Previous registered users will receive a big reduction to upgrade to the newer versions. These users should look into the details in UPGRADE.CDU. For Non-commercial users there is a POSSIBILITY to submit to one of the special contracts as explained in the file REGISTER.CDU. - Commercial usage of CDU will cost somewhat more. Also, a so called 'closed' Bulletin Board System (a system where the user must pay direct to the SysOp to get full access) is has to pay more than a Non-commercial user. Both types of users should look into the details in REGISTER.CDU; - The registration of the CDU-package will license ONE copy for use on any computer at any one time, as long as the usage confirms to the type of registration you have done (so NON-commercial usage when you have a non-commercial license); - Anyone distributing the CDU-package for any kind of remuneration must first contact the Author at the address above for authorization. - You are encouraged to pass a copy of the CDU-package along to your friends for evaluation. Please encourage them to register their copy if they find that they can use it; - Support on CDU, when used in a non-commercial environment, is available by means of written letters or by entering the inter- national echomail area DISP; - Problems and suggestions can be entered in the FidoNet <tm> Echomail conference <tm> called DISP (international). Entering this echo does not exclude you of the duty to register the CDU-package, though users who evaluate the product can enter the echo for questions; - The CDU-package, all programs, the documentation and support-files is copyrighted 1990,93 by Robert W. van Hoeven, PO. Box 131, Badhoevedorp 1170AC, Holland. All rights are reserved. You may copy this package for backup purposes. Also you may copy and share unmodified copies of the whole package, providing that the copyright notice is reproduced and included on all copies. Excluded from this statement are the support-files written by other authors. Please refer to the documentation of these programs for copyrights and license agreements; - It is forbidden to modify, adapt, translate, reverse engineer, decompile and/or disassemble the software in the CDU-package. Patching the medium at places that carry the software is seen as a program change and is also forbidden. It is forbidden to create a so called 'bypass' to skip the original introduction screens and delay. Also it is forbidden to use such a 'bypass' unless supplied by the author (Robert W. van Hoeven) himself; - Performing any of the illegal actions as stated in the previous lines, is a theft and no fair play to the author and, more important, to the registered users; - Bulletin Board Systems that distribute the CDU package can convert the WHOLE package to any archive-system they like but all original files must be included in the new archive. The CDU-package on the Bulletin Board can contain at the most 2 extra files. These files can only be a commercial for that Bulletin Board and/or validation data that is presented as a service to all users and shall have no other functions; - After the normal trial period of 30 days, you must register the soft- ware (see REGISTER.CDU) or you must remove it from your PC; - Comments, suggestions and bug reports are welcome and will be answered as soon I have the time to do so. You can send me a letter of leave a NetMail <tm> message named to Rob Van.hoeven (mind the point) on node 2:281/904 (RA Support, Monster, Holland, SysOp is Reinier de Groot). When you want to send me normal mail, address it to: Robert W. van Hoeven, PO. Box 131, 1171 AC Badhoevedorp, Holland; Also you can enter messages in the FidoNet <tm> DISP Echomail <tm> area; 1.2 Newer versions and contacting the author ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The newest version of CDU is always available at the DISP-HQ on node 2:281/904. CDU is also distributed thru a number of DISP support nodes. There are three ways of obtaining newer versions of CDU: - Logging on at DISP-HQ or a support node Look into the file SUPPORT.CDU for a full list of support nodes; - Logging on to a SDS node CDU is distributed thru SDS/SDN, but only big minors (x.10, x.20 and so on) and majors (14.01, 15.01 and so on) are submitted to the SDS distribution point in Holland; - Logging on to your own BBS; Chances are, that you will find an older version (international users) because it will take some time for the new version to 'bleed' thru the net; - Update service; You can enter a special update service (read REGISTER.CDU). If you think you have found problems in CDU, or in any other case, you wish to contact the author, you can send me: - A letter to the address you can find in the header of this file; - A NetMail <tm> message to Rob Van.hoeven (please mind the point between Van and Hoeven) at 2:281/904 or (better) 2:281/904.5; - A Message in the FidoNet <tm> DISP echomail <tm> area; ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 2 ≥ Package description and requirements ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ 2.1 Preface ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ Please notice the following: - CDU is a ShareWare product in every right way, this means this software is not crippled in any way; - These programs only works when you work with the original CATDISK.EXE program. CATDISK <tm> is (c) 1986-93 by Rick Hillier; - This release of CDU works with CATDISK 6.3x and higher releases. The older 6.2x and lower releases have a different database structure. You can try to find CDU V 1.15 (that last release that supports this format) or upgrade to the current version of CATDISK; 2.2 Requirements ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ CDU requires: - PC XT/AT/386 - At least 200K free memory but it depends on the options (picklist) you use; - DOS 3.xx and higher; (tested with 4Dos 3.02, should work with lower versions). Tested with DOS 5.0; - HDU optional ≥ - The original CATDISK program (V 7.00 or higher); 2.3 History ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ In the early '90 I got tired of my diskettes and their files. I needed a diskette catalog program. I tried a few of them, including CATDISK but all, also including CATDISK, seemed to slow for my VERY slow PC, so I did write a small program myself that was nicer than most in- memory catalog programs but did not include many options. When I finally installed a new PC at home (a 386/33DX) and also hooked on as a co-sysop for 2:281/904, my files started to grow. Because I more or less function as a remote backup for the BBS-files, my collection raised from 50 360Kb diskettes to more than 200 720/1.44 diskettes, all containing archives. I was surprised that I suddenly saw a new version of the CATDISK <tm> program (4.60 it was), and decided to try it again. By now I have created some 'small' customized programs that can help you with some tasks in CATDISK <tm> that are not available or too specialized for CATDISK <tm> to do. These programs, though they can be better, do their jobs and are now shared with you. The easiest thing you can do, is to delete them but there could be one or more that suit your needs. In any case, if you have comments or suggestions, let me know. ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 3 ≥ Installation description ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ 3.1 Installation ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The installation of the CDU package is very flexible. The first release did not contain any options but the current (and newer releases will). The installation is as follows (suggested): - Copy the *.EXE files you need (or all of them) to a directory in the DOS-path; - If you normally run CATDISK with special options (the /F[xxx] not included, this option is inserted by some of the CDU programs itself), you must create a line in your AUTOEXEC.BAT with the following format: SET CATDISK=[switch] {switch} .. {switch} Where [switch]/{switch} are the command-line options you normally use to start CATDISK. If normally you start CATDISK with /NC and /NCC, the line should be 'SET CATDISK=/NC /NCC' (without the quotes). The older CATPARM option (release 1.01) is now obsolete. It is also possible to use different CATDISK-options for all different databases you have. In this case, ignore the CATDISK switch and use ≥ the CATDiskBaseOptions option in CDU.INI; - Be sure to have CATDISK.EXE somewhere in the DOS-path. All the CDU programs will look for CATDISK.EXE in the DOS-path. If the program does not reside in the DOS-PATH, you must add a statement to the ≥ CDU.INI file (the CATDISKProgramPath option); ≥ ≥- Create a configuration file (CDU.INI) for the CDU programs. The older ≥ CDx.CTL file (or files) are now obsolete and are all combined in the ≥ CDU.INI file (see later for a description of this file) ! - Previous releases contained a program CDD.EXE. This program could not be called by that name when you run 4DOS <tm> on your system. For this reason it is renamed to CDR.EXE. You should remove any older CDD.EXE (from the CDU package!!) from your disk; - If you are going to use CDZ, you need the Colorado (CMS) tape-backup program TAPE.EXE. CDZ has been tested with the version 3.03 of this program. Older and/or newer versions *could* not be compatible with the layout of 3.03 and would cause CDZ to pass incorrect information to CATDISK. It is advised to have TAPE.EXE somewhere in the DOS-path and to use this path to call the program. If it is not, you can use a special option in CDU.INI (DOS-path access is advised though!). Please read the chapter 4.10 for a description of the tape support and some advise about settings in CATDISK <tm> when you use CDZ ! 3.2 The configuration file(s) ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ ≥All programs from the CDU package make use of ONE SINGLE configuration ≥file that is called CDU.INI. The CDU.INI file is typically a file of ≥the new generation of control-files. The syntax is derived from the ≥Microsoft Windows <tm>, MS/DOS <tm> (CONFIG.SYS) and OS/2 syntax. ≥ ≥The CDU.INI file is a normal ASCII (flat) file with records that are ≥terminated by a CR/LF combination. Most present-day (line) editors can ≥create such a file and also most word-processors have the option to ≥create a (flat) ASCII file (without control-codes!). ≥ ≥There are no formal rules for the syntax of a Windows-alike *.INI ≥file. The basic syntax though is in the form of blocks (with a ≥block-header) with options. All options between a block-header and the ≥next block-header (or the end of the file) belong to the block for ≥which the block-header gives a name. A block-header is assigned thru ≥the use of brackets before and after the name of the block. Like this: ≥ ≥[General] ≥OptionG1=value1 ≥OptionG2=value2 ≥ ≥[Custom] ≥OptionC1=value1 ≥OptionC2=value2 ≥ ≥In the example above, there are two blocks (General and Custom) which ≥are marked by their block-headers ([General] and [Custom]). The ≥options OptionG1 and OptionG2 belong to the block 'general' and the ≥options OptionC1 and OptionC2 belong to the block 'custom'. Until ≥MS/DOS 6.0 <tm> it seemed like a rule that a *.INI file could not have ≥duplicate variants of the same options. In such cases, it was common ≥to use something like this: ≥ ≥[Custom] ≥ExcludeFile-1 = A.A ≥ExcludeFile-2 = B.B ≥ ≥or ≥ ≥[Custom] ≥ExcludeFile = A.A , B.B ≥ ≥and not ≥ ≥[Custom] ≥ExcludeFile = A.A ≥ExcludeFile = B.B ≥ ≥Ms/DOS 6.0 <tm> changed this behavior. The 'MenuItem' option is an ≥example of how to break the 'rules'. DISP programs, like CDU, will now ≥use all combinations. In most cases, the variant used, is based on the ≥number of possible values. When you want to exclude more than 100 ≥files, both 'ExcludeFile = A.A, B.B, C.C......' and the form with ≥'ExcludeFile-1 =', 'ExcludeFile-2='.... and so on, are both useless. ≥In these cases, multiple (duplicate) variants of the same option are ≥used. ≥ ≥The format of the *.INI file is rather free. The block-headers must be ≥coded as given and must be enclosed in brackets. The header (and the ≥options) can start on any position in the *.INI file as long as they ≥are preceded with 'white' spaces. Options (and headers) that are ≥preceded with a comment-character ('%'), are not used, nor are empty ≥lines and invalid options ! The options have the format: ≥ ≥Optionname = value ≥ ≥The '=' character is used to separate the option and its value(s). If ≥multiple values precede the '=' character, they are separated by a ≥comma or another character (like Optionname = value,value,value). The ≥number of white spaces between the optionname and the '=' character ≥and the '=' character and the value(s) is irrelevant. An option will ≥never exceed one line and a line can never be more than 255 characters ≥long. The case (upper/lower) of all options, block-headers and values ≥is not important, unless specified. ≥ ≥The names used thru all DISP <tm> products are as follows: ≥ ≥- Block-name ≥ The name of the block that is preceded with a block-header and will ≥ be active until the next block-header or the end of file (which ≥ comes first); ≥ ≥- Option ≥ The name of the options within a block; ≥ ≥- Parameter or values ≥ These are the actual values that belong to an option. Sometimes they ≥ are called parameter, but most of the time we will call them a ≥ value. ≥ ≥The descriptive syntax of all options is: ≥ ≥[.....] this value is MANDATORY, it MUST be present and have a valid ≥ value; ≥ ≥{.....} this value is OPTIONAL. If it is NOT present, some default ≥ is used; ≥ ≥'value' Values between quotes must be coded WITHOUT the quotes ≥ themself, UNLESS specified; ≥ ≥The DISP programs (including the programs in the CDU package) will ≥look for the control-file (CDU.INI in case of the CDU package) in the ≥following way: ≥ ≥- First the current directory is searched for the CDU.INI file; ≥ ≥- If not present in the current directory, a search thru the DOS-path ≥ is performed until the CDU.INI file is found; ≥ ≥- If the CDU.INI file is not found in the current directory and/or the ≥ DOS-path, the directory where the EXE-file resides (if this is not ≥ the same directory as the current directory) will be examined. This ≥ search is only performed with DOS releases 3.xx and higher; ≥ ≥It is advised to place the CDU.INI file alongside the programs and/or ≥somewhere in the DOS-path. ≥ ≥The following chapter will contain the various statements you can ≥use in the file. 3.3 INI options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The next chapters contain the options for all programs in the CDU package. The descriptions are grouped together in the same blocks as they have to appear in CDU.INI. Please refer to the example CDU.INI that is supplied with this package ! 3.3.1 [General] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, must be defined inside the block with block-header [General] ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ RegistrationName = [name] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : This option is only valid after you have registered the package and received a key. For non-registered usage, this statement must not be included. If you have specific control-files, you must include this option in all of these files ! ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ TempDirectory = [dir] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : The various programs in the CDU package will create one or more temporary files. Normally these are placed in the CURRENT directory unless you specify THIS option. [dir] Must point to a valid directory. The programs will test if the directory is available and will abort if this is not the case. You can use relative paths ! ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ SwapDirectory = [dir] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : Some of the programs in the CDU package will call CATDISK <tm> itself. Before CATDISK <tm> is called, the program will first swap itself from memory. This will go in the order XMS, EMS and DISK. DISK is only used when there is not enough XMS or EMS work-space available. When swapping to DISK, the program will create a temporary file. This file will normally be placed in the CURRENT directory unless this option is made active. [dir] Must point to a valid directory. The programs will test if the directory is available and will abort if this is not the case. You can use relative paths ! ≥⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥≥ UseEMS = [true | false] ≥ ≥¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ≥Usage : Some of the programs in the CDU package will swap out of ≥ memory while they call the external program (CATDISK.EXE in ≥ most of the cases, otherwise CDT.EXE or TAPE.EXE). ≥ ≥ Normally the swap routine will use XMS (first), EMS (second) ≥ or DISK (third), depending on the available resources. ≥ ≥ If you don't want to use EMS as a candidate for swapping, you ≥ should supply 'UseEMS = false' or 'UseEMS = N' (both are valid ≥ values for this option). ≥ ≥ Based on the type of swap (the DOS-shell will NEVER use XMS, ≥ only EMS or DISK), EMS is disabled as one of the memory ≥ candidates of swapping. ≥ ≥ CDF will also use EMS or XMS. If UseEMS and/or UseXMS are ≥ false, CDF will not use this type of memory. ≥ ≥ The default (when you don't supply the option in CDU.INI) is ≥ to use EMS when selected, available and when enough EMS memory ≥ is available. ≥ ≥ You can supply both UseEMS and UseXMS together, to allow ≥ either any type of memory (both set to true), one type of ≥ memory (one set to true, the other to false) or NO type of ≥ memory (both set to false). ≥ ≥ ≥⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥≥ UseXMS = [true | false] ≥ ≥¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ≥Usage : Some of the programs in the CDU package will swap out of ≥ memory while they call the external program (CATDISK.EXE in ≥ most of the cases, otherwise CDT.EXE or TAPE.EXE). ≥ ≥ Normally the swap routine will use XMS (first), EMS (second) ≥ or DISK (third), depending on the available resources. ≥ ≥ If you don't want to use XMS as a candidate for swapping, you ≥ should supply 'UseXMS = false' or 'UseXMS = N' (both are valid ≥ values for this option). ≥ ≥ Based on the type of swap (the DOS-shell will NEVER use XMS, ≥ only EMS or DISK), EMS is disabled as one of the memory ≥ candidates of swapping. ≥ ≥ The default (when you don't supply the option in CDU.INI) is ≥ to use EMS when selected, available and when enough EMS memory ≥ is available. ≥ ≥ You can supply both UseEMS and UseXMS together, to allow ≥ either any type of memory (both set to true), one type of ≥ memory (one set to true, the other to false) or NO type of ≥ memory (both set to false). ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ CATDISKProgramPath = [path] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : Normally, the CDU utilities will search for CATDISK.EXE in the DOS-path (some older versions even required that CATDISK.EXE should be in the same directory as the CATDISK databases). If CATDISK.EXE is NOT inside the DOS-path or the search in the DOS-path is slow (XT and slow HDU's), you can add this option that must point to the location AND name of CATDISK.EXE. [path] Must point to the valid directory and file-name of the CATDISK program. ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ CATDISKBaseDirectory = [dir] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : Older versions of CDU used the CATBASE environment parameter to locate the directory that contained the CATDISK databases. This method is obsolete in CDU version 3.01 and higher. You MUST assign the directory by means of this option ! [dir] Must point to the valid directory that contains the CATDISK databases. 3.3.2 [CDC] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, must be defined inside the block with block-header [CDC]. Currently there are NO options for CDC. You can set the [CDC] block header though ! ≥3.3.3 [CDE] options ≥ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ ≥The following options, if defined, must be defined inside the block ≥with block-header [CDE]. ≥ ≥Currently there are NO options for CDE. You can set the [CDE] block ≥header though ! 3.3.4 [CDF] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, must be defined inside the block with block-header [CDF]. Currently there are NO options for CDF. You can set the [CDF] block header though ! 3.3.5 [CDM] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, must be defined inside the block with block-header [CDM]. ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ DisketteClusterSize-1 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-2 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-3 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-4 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-5 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-6 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-7 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-9 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-9 = [minsize],[maxsize],[clustersize] ≥ ≥ DisketteClusterSize-10 = [minsize],[maxsize],[clustersize] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : Normally, CDM will use a clustersize of 512 bytes for diskettes with a high density and 1024 bytes for low density diskettes. If you use specific cluster sizes or abnormal diskette formats, you can supply up to 10 different formats with their cluster sizes. Any of this 10 options must have a unique option-name (see above). [minsize] The minimum available space (when formatted) for this diskette format (like 1.400.000 for a 1.4 Mb diskette); [maxsize] The maximum available space (when formatted) for this diskette format (like 1.499.999 for a 1.4 Mb diskette); [clustersize] The size of each cluster on diskettes that have between [minsize] and [maxsize] bytes; When you use normal formatting routines, you do not have to supply any of this options. ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ DirectoryToDatabase = [dir],[base] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : CDM can move files from the hard-disk to the diskettes. Normally CDM will ask which CATDISK <tm> database has to used and which drive will contain the diskettes (unless /BASE and/or /DRIVE are supplied). In some configurations the user uses a different approach. In these configurations, users store the files for a SPECIFIC CATDISK <tm> database in a SPECIFIC directory (for example, the files that will go to the WIN3 CATDISK <tm> base will always be placed in F:\ZIP\WIN and the files that go to the FSIM CATDISK <tm> base will always be placed in the F:\ZIP\FSI directory). When this is the case in your setup, you can use this option. [dir] Must contain the name of the directory on hard-disk where the files for the SPECIFIC CATDISK <tm> base [base] will be stored; [base] Must contain the name (no extension) of the CATDISK <tm> base where the files in directory [dir] on hard-disk will go to; ≥ Previous releases (2.11 and lower) also used an optional ≥ parameter {drive} to assign a drive letter of diskettes to be ≥ cataloged, in combination with the directory and database ≥ name. This parameter is obsolete in versions 3.01 and higher ≥ and is replaced by the CATDISKBaseDrive option (see later). Based on the previous examples with WIN3 and FSIM, you could code: DirectoryToDatabase = F:\ZIP\WIN,WIN3 DirectoryToDatabase = F:\ZIP\FSI,FSIM After you have swapped to the correct directory (f.i. the F:\ZIP\WIN directory) and CDM is started, CDM will detect that the current directory (F:\ZIP\WIN) matches one of the DirectoryToDatabase options and will move the files to the correct diskettes. It will then catalog this diskette in the WIN3 database. If CDM can not find a match (so the current directory does not match any of the DirectoryToDatabase options), CDM will ask which database must be used (unless /BASE is supplied) and which diskette-drive must be used (unless /DRIVE is supplied). ≥⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥≥ ExcludeForProcessing = [mask]{,[mask]}{,[mask]}.....{,[mask]} ≥ ≥¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ≥Usage : Certain files in the directory on hard-disk that will be moved ≥ to diskette by CDM, have to be excluded from this process. One ≥ typical file is DESCRIPT.ION which is created by NDOS <tm> and ≥ 4DOS <tm>. This file is automatically excluded by CDM but ≥ others, like FILES.BBS, FILEDESC.LOG and so on, are not. If ≥ you want to exclude one or more files from processing (e.g. ≥ movement from hard-disk to the assigned catalog), you must ≥ include this option. You can supply up to 20 file-masks which ≥ can contain full names (no directories) or names with wildcard ≥ characters. ≥ ≥ [mask] Must be set to a full filename or a partial filename ≥ with valid wildcards (DISP formats are included). You ≥ must not supply a directory-name or drive letters. ≥ ≥ If you exclude files from processing, by means of this option, ≥ it will NOT mean that this files won't trigger CDT (see next ≥ option). If they are included in the TriggerCDTOnFile option, ≥ CDT will still trigger. ≥ ≥ ≥⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥≥ TriggerCDTOnFIle = [mask]{,[mask]}{,[mask]}.....{,[mask]} ≥ ≥¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ≥Usage : In some cases, the directory you process, also contains one or ≥ more files with descriptions of these files. Normally CDT can ≥ be used to add these comments to the CATDISK database. You can ≥ also automate this process. If you include the ≥ TriggerCDTOnFile option with one or more masks (full or ≥ partial filenames), CDT will be called by CDM when one or more ≥ (or all) of these mask match a file in the directory on ≥ hard-disk AFTER all files have been moved to diskettes. If you ≥ do NOT exclude these files for processing (with the ≥ ExcludeforProcessing option), CDT will NEVER trigger because ≥ these files are moved to diskette UNLESS you entered 'N' on ≥ the question if the move is OK ! ≥ ≥ [mask] Must be set to a full filename or a partial filename ≥ with valid wildcards (DISP formats are included). You ≥ must not supply a directory-name or drive letters. If ≥ you start the full or partial filename with a '|' ≥ character (piping character), CDM will delete the file ≥ after CDT has been called. If you do NOT include this ≥ character, the file is left on the hard-disk. ≥ ≥ ≥⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥≥ CDTPRogramPath = [path] ≥ ≥¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ≥Usage : If CDM has to call CDT.EXE (see above) and the CDT.EXE program ≥ can not be found in the normal way (current directory, thru ≥ the DOS-path or in the directory where CDM.EXE resides), you ≥ must include this option. The format is the same as the ≥ previous CATDISKProgramPath option. 3.3.6 [CDR] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, must be defined inside the block with block-header [CDR]. ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ ToOldFiles = [mmyy] ≥ ≥ ToOldFiles = [-mm] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : CDR can (optionally) remove files based on the mask AND age. When you want to remove selected files based on age, you can supply the ToOldFiles option (or the /TOOLD= command-line parameter). You can use only one of the two different formats. The first format will decide the removal based on a fixed date (month/year), the second format will decide based upon a relative date ([current date] - [X-months]). [mmyy] With this format, you supply the actual date which is considered as to old. All files of this date and older will be marked as to old. mm is the month (always 2 digits, 01-12) and yy is the year (always 2 digits, 80-99); [-mm] With this format, you supply the number of months that must be subtracted from the current date to create the date that is considered as to old. The minus-sign is mandatory and the number of months 'mm' can be anything between 1 and 65534; CDR can use the /TOOLD=- command-line switch (watch the minus sign without a number) to switch the ToOldFIles option in the control-file to OFF. ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ ExcludeFileForRemoval = [base],[mask] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : When you use CDR to clean your diskettes from files that are old or need to be removed for some other reason, you will need to enter 'N' (no) for each file that matches the criteria but has a special meaning for you and must be kept on diskette. For example, very special GIF's that you want to keep, one or more utilities that never 'age' like archive-programs and so on. To overcome the problem of entering 'N' for each of these files EVERY time you run CDR (with the /TOOLD option or the equivalent CDU.INI option), you can exclude these files with one or more ExcludeFileForRemoval options. These options will work for ALL various databases that you have or for just one (depending on the way you code the option). If a file matches the criteria (mask and/or the file is too old) but also matches one or more of the ExcludeFileForRemoval options, the file will be shown on the screen but can not be selected (it is skipped). [base] This must be the name of the database for which the exclusion will work. You must either code the full name of the database (without extension, fi. ARCH and NOT ARCH.DTA) or you must code an asterix ('*') in which case this exclusion will work for ALL databases; [mask] This must be a valid file-mask (wildcards are allowed) which will be excluded by CDR. You can use the normal DOS wildcards AND the special DISP-compatible '=' wildcard to do a shifting match (=TA will match mTA.exe but also TAnd.zip, maTAhar.arc, test.dTA and so on); The number of these options (per database) is only limited by the available conventional memory that is available when CDR is running. When you run CDR.EXE, you can exclude any new match on the fly by using the 'E' answer. In that case CDR will add the new entry (for the database you are working on) to the CDU.INI file which was used at the start of CDT.EXE. If there wasn't any CDU.INI file at startup, CDR.EXE will create a new one for you and will signal you at the end of the run that the file has been created ! Some examples. Given: ExcludeFileForRemoval * PK*.* ExcludeFIleForRemoval ARCH ARC*.* Will exclude any match on PK*.* in ANY database and will also exclude any match on ARC*.* in the ARCH database. 3.3.7 [CDS] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, must be defined inside the block with block-header [CDS]. Currently there are NO options for CDC. You can set the [CDC] block header though ! 3.3.8 [CDT] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, must be defined inside the block with block-header [CDT]. ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ GlobalChange [[from] [to]]{,[[from],[to]]}....{,[[from],[to]]} ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : CDT can change text in the comment-file BEFORE it is passed to CATDISK <tm>. This is needed most of the time. Most files you have received are converted from one archive system to another and when you download a comment-file from a BBS, it is possible that the BBS uses ZIP and LZH as where you use ARJ and already converted the LZH/ZIP file to ARJ. In this case the file will be in the CATDISK <tm> database with .ARJ as the extension and no match will be found if it is in the comment-list with the .ZIP extension. GlobalChange can change one item to another one. [from] is the text in the comment-file you want to change. It must be one continuous text and the match is depending on the case; [to] is the text that will replace the [from] text when a match with [from] is made. If there are more matches on one line (record) all matches are changed. On the GlobalChange option you must always code sets of changes that are separated by a space and the sets are separated by a comment. The function of GlobalChange is case sensitive ! When you are not sure, include both the lower-case and upper-case values. For example, change all ARJ/LZH archive extensions into .ZIP: GlobalChange = .ARJ .ZIP , .arj .ZIP , .LZH .ZIP , .lzh .ZIP When you add the comment-file to more than one database (see later), you don't have to be afraid that CDT will do too much work. The changes to the comment-file are only made once and this new file be passed to CATDISK <tm>. Also the original file will not be changed ! ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ FileListUpdate=[mask] [base] [sf] [ef] [sd] [ed] [sv] [ev] [sc] [ec]≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : When you look at the 'Import Comment' option in CATDISK, you can see that a number of parameters must be passed to CATDISK. The FileListUpdate option includes all these parameters for a given file [mask] and a given CATDISK database [base]. Because CDT matches your comment-file with [mask], it will know which database (or databases, you can include multiple FileListUpdate options for the same [mask] but different [base]) must be updated with these comments. [mask] This must be a valid DOS mask that matches one or more comment-files (ALLFILES listings); [base] This must be the name of the CATDISK <tm> database (no extension) that must be updated with the comments from this file; [sf] This is the starting position of the filename in the comment-file; [ef] This is the ending position of the filename in the comment-file; [sd] This is the starting position of the directory in the comment-file. Normally this is set to 0; [ed] This is the ending position of the directory in the comment-file. Normally this is set to 0; [sv] This is the starting position of the volumeID in the comment-file. Normally this is set to 0; [ev] This is the ending position of the volumeID in the comment-file. Normally this is set to 0; [sc] This is the starting position of the comment in the comment-file; [ec] This is the ending position of the comment in the comment-file; Some examples for updating various databases (I used database names with 4 characters) with comments from various files, are found in the example CDU.INI file. If you use CDM to call CDT, you must make sure that there is a [mask] available for the file you trigger CDT for (see CDM). ≥ There is one SPECIAL declaration. DESCRIPT.ION (NDOS <tm> or ≥ 4DOS <tm>) does not adhere to the rules that CATDISK applies ≥ (the description starts on a shifting location). For this ≥ reason, CDT will always convert DESCRIPT.ION files to an ≥ internal format, where the file starts at position 1 and the ≥ description at position 14. You still have to include entries ≥ for DESCRIPT.ION though ! 3.3.9 [CDZ] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, must be defined inside the block with block-header [CDZ]. ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ TapeProgramPath = [path] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : If you use CDZ, this program has to use TAPE.EXE from Colorado (the Jumbo version, though the versions for other types from this company could also work). CDZ has been tested with version 3.03 of the Jumbo software (TAPE.EXE). It is advised to have TAPE.EXE somewhere in the DOS-path and let CDZ search for the program. If this is not your normal setup, and/or you have renamed TAPE.EXE to another name, you must supply this TapeProgramPath option. [path] must point to the drive, directory and filename of the TAPE.EXE program (or the renamed version of it, if you did rename TAPE.EXE to something else): CDZ will call TAPE.EXE (or the equivalent) thru the DOS-shell (COMMAND.COM or 4DOS.COM or alike file). To do so, it will use the setting of the COMSPEC environment variable ! 3.3.10 ['database'] options ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ The following options, if defined, can be contained inside a block with a block-header that carries the name of the CATDISK database that it belongs to. So if you have 2 databases (CATDISK.DTA and ARCHIVE.DTA), you can define 2 blocks ([CATDISK] and [ARCHIVE]). See the example in CDU.INI (the [ARCH] and [PASC] blocks). ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ CATDISKBaseOptions = [options] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : You can use different CATDISK <tm> options for all the databases you have. For example, you have a database ARCH which contains all archive file PLUS the in-archive files but you also have a database GAME where you only log the archive files but NOT the in-archive files. This can all be done with help of one or more of the CatDiskBaseOptions options. [options] These are the CATDISK <tm> options that apply for the database [base]. Any space between options must be coded as an underscore character, like NC_NCC; For example you want archive directories (in-archive files) to be stored for the ARCH database but not for the GAMES database. The default extraction method you installed with CDISKCFG was not to extract the archive directory. In CDU.INI you can now set: [ARCH] CATDISKBASEOPTIONS = /ALLFILES In which case /ALLFILES will be added as a command-line when any of the CDU programs will call CATDISK for database ARCH ! You can use the these options to overcome the need for a CATDISK environment variable. Be warned though that both the CATDISK environment variable AND the options on the correct CatDiskBaseOptions option will BOTH be passed to CATDISK whenever a CDU program will call CATDISK ! ⁄ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ CATDISKBaseDrive = [drive] ≥ ¿ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ Usage : When you use different drives for different CATDISK catalogs (for example, your ARCH database obtains the info from your 3 1/2" A-drive and GAME needs the info from the 5 1/2" B-drive) you can set the correct drive by using the /DRIVE= command-line parameter. You can also connect databases to drives with the CatDiskBaseDrive options. [drive] This must be the drive-letter (without :) for the drive that is always used when [base] is manipulated. ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 4 ≥ Runtime information ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ 4.1 General program description ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ All programs described below work more or less the same. If you have more than one CATDISK <tm> database, you can select to point to the wanted database by means of a command-line switch (/BASE=) or by means of a PICK-list. If you have more than one database and you do NOT supply the /BASE= parameter, the program will show a PICK-list with all eligible databases. Just move the bar to the right database and hit the [ENTER] button. All programs have some common command-line para- meters that can be used. You can use /?, /H, ? or H to display the valid command-line parameters for each of the programs. All CDx programs that use a file-mask, contain one EXTRA mask that is normally not available in DOS. The '=' mask can be used for a 'shifted' test. Some examples explain it best: =RA will select tRAns.arc, RA_101.zip, warnRAm.arj and so on =A.E will select mamA.Exe and so on; You can not combine the '=' mask with other masks like ?? and ** ! 4.2 CDC ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ CDC is the smallest and easiest program. Sometimes the CATDISK <tm> databases will contain 'garbage' characters in some fields. Though it should be fixed, it is still possible that your databases contain these characters. These characters do no harm but they can be a pain in the neck in the case when you want to compress your CATDISK <tm> database(s). If you use programs like DIET or the resident STACKER, you can get some extra bytes of compression back when the fields in the CATDISK <tm> databases are set to hex '00' for that part of the field that is NOT in use. This is also the case when your hard-disk is converted to a DOUBLESPACE disk. CDC should be run once in a longer period and does nothing more than cleaning all garbage in the CATDISK <tm> database. It should not al- ter the active information but when you are unsure, you must backup the database first. CDC works with the following command-line options: /BASE=nnnnnnnn You can use this parameter to point to the right CATDISK <tm> database. [nnnnnnnn] is the name (without extension) of the database. If there is only one database, CDC will use it at once. If there are more databases and you don't use this parameter, CDC will show all possible databases and you can pick one of them; /BASELOC=lllll This option can overrule the location of the CATDISK databases that was set with the CDU.INI options. ≥4.3 CDE ≥ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ ≥CDE is a simple program that can help the poor user who has multiple ≥databases which all need various parameters. For example, your ARCH ≥database need diskettes in drive A and uses /NC but in-archive files ≥don't need to be included in the database. Another database (GAME), ≥needs drive B, also /NC but in this case you need to include the ≥in-archive files. ≥ ≥Under normal conditions, this would be a very tedious work when you ≥only use the CATDISK <tm> program. Every time you need to set or reset ≥some or more parameters. You could solve it with several batch files, ≥but all parameters *could be* already available in CDU.INI. ≥ ≥CDU.INI CAN contain specific parameters for each individual database ≥(The CATDISKBaseOptions and CATDISKBaseDrive parameters) in the ≥specific block for such a database. You can enhance the usage of these ≥parameters beyond the usage by CDM, R, S, T and Z if you would have a ≥small program that only called CATDISK <tm> and passed these ≥parameters to CATDISK. This is what CDE will do for you (CDU Execute ≥CATDISK program). ≥ ≥CDE will take the options from CATDISKBaseOptions and CATDISKBaseDrive ≥parameters and will pass these to CATDISK.EXE. CATDISK.EXE is called ≥in a swapped shell, so there will be 4K less of conventional memory ≥for CATDISK as when you would execute CATDISK.EXE directly ! CDE will ≥pass the parameters in the order: ≥ ≥/F[database] /[drive] [parameters from CDU.INI] [parameters in cmdline] ≥ ≥/[drive] is only passed when the CATDISKBaseDrive option is set for ≥this specific [database] and [parameters from CDU.INI] will only be ≥passed when the CATDISKBaseOptions option is set for this specific ≥[database]. [parameters in cmdline] will only be passed if you supply ≥extra parameters on the commandline for CDE. CATDISK itself will use ≥the CATDISK environment variable. These will also be taken into ≥account by CATDISK itself. ≥ ≥ ≥The general calling syntax for CDE is: ≥ ≥CDE [databasename] {extra parameters} ≥ ≥[databasename] Is mandatory and is the name (without extension) ≥ of the CATDISK <tm> database. You can supply any ≥ extension but it will be stripped by CDE. Examples ≥ are CATDISK, ARCH and not CATDISK.DTA or ARCH.SUM. ≥ ≥{extra parameters} These are the extra options that you can supply. ≥ These can be any valid CATDISK parameters (see ≥ CATDISK /? for a list). ≥ ≥CDE (like all other programs that call CATDISK), will use either XMS, ≥EMS or disk to swap itself out of memory. 4.4 CDF ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ CDF looks much like CATDISK internal file-list but it is somewhat faster and has some extra options. You can use the movement keys to scroll left, right, up and down the list and you can use up to 50 masks in one run. Also the enhanced masks can be used ('='). One extra option makes it possible to show the diskettes in free-space order so you can easy select a diskette that can fit your new file(s). CDF works with the following command-line options: /BASE=nnnnnnnn the same as with CDC /BASELOC=lllll This option can overrule the location of the CATDISK databases that was set with the CDU.INI options. /FREE Only show diskettes in free-space order /ARC Display in-archive files also; /ALL Search for file-mask in ALL available CATDISK <tm> databases which are in the installed directory. CDF will use ALL *.DTA files for the search. /SD Sort the file-list on filedate (ascending). Within the sorted list, files are sorted on filename. /SV Sort the file-list on VolumeID (ascending). Within the sorted list, files are sorted on filename. /SA Sort the file-list on Archives (ascending). Within the sorted list, files are sorted on filename. /SS Sort the file-list on size (ascending). Within the sorted list, files are sorted on filename. 4.5 CDM ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ CDM is something you must try. Put all new files that have to go to diskette into one directory on your hard-disk (use separate directories for files that will go into separate diskette-sets e.g. CATDISK <tm> databases). Start CDM. CDM will first try to look if older versions are already inside the diskette collection (e.g. SCAN82 is on ARCHIVE 10 and now you have SCAN83 ready to store on diskette). For equal files, CDM will ask if you want to delete the file from hard-disk (answer 'Y'). If you reply 'N', CDM will add the file to one of the diskettes and BOTH (name-like) versions will reside on diskette. If you answer 'A', CDM will remove the file from diskette and will add the one from hard-disk to a new diskette !! The algorithm to detect different versions is far from perfect. Only files with names of 5 bytes or longer (excluding the extension) and with the last 3 bytes unequal but the first bytes equal, are marked. So, CT21 and CT53 are not detected but MTA_VE14 and MTA_VE16 are. Now CDM will try to fit the new files on your diskettes in a way that the diskettes are filled optimal. This all will only use one mount per eligible diskette. After a diskette is ready, CDM will call CATDISK so you can update the database. CDM works at my place but not everybody will store files in the way I do, so try before you use. CDM works with the following command-line options: {directory-name} When you supply a (valid) directory-name in the command-line options, CDM will start to work in THAT directory and will also try to match THAT directory with any DIRECTORYTODATABASE option that you may have supplied; ≥{path/filemask} You can supply a file-mask to CDM. Normally CDM will ≥ use *.* as the default mask (all files), but it is ≥ possible to just select one or a number (with a ≥ file-mask with wildcards included). You can combine ≥ the filemask with the {directory-name} or without. ≥ Some examples: ≥ ≥ CDM F:\ZIP\*.ZIP ≥ CDM ≥ CDM *.ARK ≥ CDM MYFILE.INI ≥ CDM ..\MYFILE.DAS /BASE=nnnnnnnn the same as with CDC /BASELOC=lllll This option can overrule the location of the CATDISK databases that was set with the CDU.INI options. /DRIVE=d the same as with CDR /NORESTART When you terminate CDM while CDM is busy with the manipulation of diskettes (the second part), you can start CDM again and it will go on as if nothing has happened. Any selection screens are skipped and CDM will go on with the next volume in the list. If this is NOT what you want, you can supply /NORESTART and CDM will start from scratch again. If you did finish CDM in a NORMAL way (not pressing ESC), the restart files are scratched and CDM will start from scratch the next time. You can also force CDM to start from scratch (after abnormal termination) by deleting the files CDM$$???.??? from disk; /MANUAL Normally CDM will start an automatic sequence to pass the actions to CATDISK <tm>. This will work only partial when you run a non-registered version of CATDISK <tm>. In this case you can (must) add /MANUAL to the command-line. The CDM program will NOT pass the /CATALOG, /QUIET, /NOSHELL, /NP, /NW, /NT and /NS command-line options to CATDISK <tm>, so you are on your own when CATDISK <tm> is called; ≥Based on the parameters in CDU.INI, you can exclude one or more files ≥from being moved to the diskette collection (CDM will ignore them), is ≥it possible to mark some files as triggers to call CDT (in which case ≥CDT must have knowledge of the internal file-format) and will CDM look ≥if there is a FILES.BBS inside the directory. If the latter is true, ≥CDM will remove entries from FILES.BBS of those files that have been ≥moved to diskette. ≥ ≥CDM will sometimes display comments at the bottom of the screen. It ≥will look in FILES.BBS, DESCRIPT.ION or any DISP-compatible *.I?? ≥comment-file (in this order) for a file-comment. ≥ ≥CDM will ALWAYS exclude DESCRIPT.ION from the movement process ! 4.6 CDR ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ CDR is a nifty utility that can help you to clean your diskette files. CDR is the CATDISK <tm> delete utility. In general, you can use this program in 2 ways. - Normal delete (with extra mask) You will start CDR with one or more file-masks to delete; - Date-delete You can delete files that are older than a certain month and year; When CDR is started, it will search the database for all matches (you can supply up to 50 ! masks) and will sort them on volume-ID after you have been presented with a question if one or more (or even all) of the matched files have to be deleted. Then CDR will ask you to mount the first volume, the next volume and so on. CDR will combine all files on one volume so you only have to mount diskettes only once. They will be asked in volume-ID sorting order and only diskettes that contain files to be deleted are asked for a mount. After the file(s) are deleted for a specific volume, CDR will call CATDISK <tm> and you can update the catalog with the original CATDISK program. CDR works with the following command-line options: /BASE=nnnnnnnn the same as with CDC /BASELOC=lllll This option can overrule the location of the CATDISK databases that was set with the CDU.INI options. /TOOLD=mmyy mmyy is a valid (4 digit) month and year. When you supply this parameter, CDR will only delete files that equal one of the masks AND are OLDER than the supplied mmyy combination; /TOOLD=-mmm The -mm format uses a relative date. In this case mm months are subtracted from the current date and will create the new date that is considered as the first date that is to old. [mmm] can be anywhere between 1 and 65534 (far back in time, we then acted and looked like monkeys); /TOOLD=- This option is used to switch the ToOldFiles option in either CDU.INI to off; /DRIVE=d CDR would like to know the drive that contains the diskettes that are worked on (delete files). If you do not supply the option, CDR will ask for the drive-letter; /NORESTART When you terminate CDR while CDR is busy with the manipulation of diskettes (the second part), you can start CDR again and it will go on as if nothing has happened. Any selection screens are skipped and CDR will go on with the next volume in the list. If this is NOT what you want, you can supply /NORESTART and CDR will start from scratch again. If you did finish CDR in a NORMAL way (not pressing ESC), the restart files are scratched and CDR will start from scratch the next time. You can also force CDR to start from scratch (after abnormal termination) by deleting the files CDR$$???.??? from disk; /MANUAL Normally CDR will start an automatic sequence to pass the actions to CATDISK <tm>. This will work only partial when you run a non-registered version of CATDISK <tm>. In this case you can (must) add /MANUAL to the command-line. The CDR program will NOT pass the /CATALOG, /QUIET, /NOSHELL, /NP, /NW, /NT and /NS command-line options to CATDISK <tm>, so you are on your own when CATDISK <tm> is called; 4.7 CDS ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ This is a nice utility if you get many request for copies of your files. CDS will sort the files from new to old, will ask if you would like to select each individual file and will show the number of bytes you have selected. When you stop selecting files, CDS will start to ask for diskettes and will copy files from the diskette to the current directory. Also a FILES.BBS alike file, containing any comments from the CATDISK <tm> database you selected, is copied onto the disk. CDS works with the following command-line options: /BASE=nnnnnnnn the same as with CDC /BASELOC=lllll This option can overrule the location of the CATDISK databases that was set with the CDU.INI options. /DRIVE=d the same as with CDR /DEL if supplied, CDS will not COPY the file from diskette but will MOVE the file. In this case CATDISK <tm> itself will be called to update the changed diskette in the CATDISK <tm> database. With this option you can select a set of files from a certain database, move them to hard-disk (also a FILES.BBS file is created), use CDM to merge these files in a new database and use CDT to update the comments from the FILES.BBS file in this new database; /NORESTART When you terminate CDS while CDS is busy with the manipulation of diskettes (the second part), you can start CDS again and it will go on as if nothing has happened. Any selection screens are skipped and CDS will go on with the next volume in the list. If this is NOT what you want, you can supply /NORESTART and CDS will start from scratch again. If you did finish CDS in a NORMAL way (not pressing ESC), the restart files are scratched and CDS will start from scratch the next time. You can also force CDS to start from scratch (after abnormal termination) by deleting the files CDS$$???.??? from disk; 4.8 CDT ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ This is a nice utility if you get ALLFILES listings that will be used to add comments to your CATDISK <tm> database(s). It needs the CDU.INI to do its work (FilelistUpdate and GlobalChange options inside this file). CDT is called with the following syntax: CDT [file] {/MANUAL} [file] Must be the complete filename (optionally you can add the path and drive but the complete name can not be longer than 40 bytes) of the comment-file that contains the comments that must be imported; /BASELOC=lllll This option can overrule the location of the CATDISK databases that was set with the CDU.INI options. /MANUAL Normally CDT will start an automatic sequence to pass the actions to CATDISK <tm>. This will work only partial when you run a non-registered version of CATDISK <tm>. In this case you can (must) add /MANUAL to the command-line. The CDT program will NOT pass the /CATALOG, /QUIET, /NOSHELL, /NP, /NW, /NT and /NS command-line options to CATDISK <tm>, so you are on your own when CATDISK <tm> is called; The normal rules for the text-files apply. CATDISK can only use the first 32767 lines. The file must be a text-file (no tabs and lines not longer than 255 bytes). CDT will NOT read (and/or process) the text-file itself in any way. It will only parse the CDU.INI file and will supply the correct calls to CATDISK. If you are running a non-registered CATDISK <tm>, you must use the following sequence after CATDISK <tm> is called by CDT: - Pass the intro-screen; - Press <9>; - Press <F10>; - Press <ESC> a couple of times (CDT will flush the keyboard after CATDISK <tm> exits back to CDT; ≥CDT will use a special algorithm if you include an entry for the file ≥DESCRIPT.ION (NDOS, 4Dos description file). In this case, CDT will ≥(internally) convert DESCRIPT.ION to a file with a fixed format, where ≥the filename starts at position 1 and the description at 14. If you ≥want to include DESCRIPT.ION descriptions in CDT, you MUST supply an ≥entry for this file (in the normal way) with the values described ≥above ! Registered CATDISK <tm> users can sit back and relax (why shouldn't YOU register CATDISK and CDU ?). 4.9 CDZ ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ CDZ makes CATDISK <tm> even more useful. Until now, CATDISK <tm> could store information of any logical drive (diskette, hard-disk, whatever has a drive-letter) but with help of the CDZ utility, you can also access your TAPE device. The 2.01 version of CDZ (the first) is a somewhat 'rudimentary' version in the way that it only supports the CMS (Colorado Memory Systems) JUMBO 120 and JUMBO 250 tape-drives. The majority of non-commercial setups use such a tape-drive though. Anyway, make sure to read the included HELPTAPE.ME! file ! What CDZ does, is, with help of the CMS TAPE.EXE (Jumbo version 3.03), obtain the information from your tapes and convert this information into CATDISK databases which can be accessed thru CATDISK <tm> ! CDZ is called with the following syntax: CDZ {/BASE=nnnn} {/BASELOC=llll} {/NOFILES} {/TAPENAME=vvvv} {/TAPECOMM=cccc} /BASE=nnnnnnnn the same as with CDC (see documentation on CDC above) /BASELOC=lllll This option can overrule the location of the CATDISK databases that was set with the CDU.INI options. /NOFILES Normally CDZ will obtain all information from the tape in question. All information means: - All volumes on the tape (and their description) - All files inside all volumes (when they are compatible with the QIC-40/80 backup strategy) This process can take very long (up to 15 to 20 min. per tape, mostly because TAPE.EXE takes very long to initialize the tape-drive and ALL volumes need to be listed in sequential order). When you specify /NOFILES, CDZ will only obtain all volume-related information from the tape (see 4.10 for a description of volumes, files and tapes) and will skip the search for files inside the volumes. This causes TAPE.EXE only to be executed once for every tape, thus taking between 1 and 3 minutes for each tape. The information inside the CATDISK database will contain all volumes AND THEIR DESCRIPTION (the most important). /TAPENAME=vvvv You can run CDZ unattended. Normally CDZ will need to know the name of the tape (this can not be obtained thru TAPE.EXE when called from a program) which must be entered manually. You can skip the manual answer when you supply the name of the tape 'vvvvv' with the TAPENAME command-line option. Any spaces must be coded as underscore ('_') characters and the tape-name must be 1 to 11 positions. For example: /TAPENAME=TAPE_001 Will skip the question in CDZ and catalog the current tape as 'TAPE 001' in the database. To run fully unattended, you also need to supply /BASE on the command-line when you use more than one database. /TAPECOMM=vvvv As with /TAPENAME, this option is meant to be used as an option to run unattended. You can supply the new summary comment for the tape to be processed. This is a new option in CATDISK <tm> version 7.0 ! If you are RECATALOGING a tape and the old tape in the database already had a summary comment, that comment will be used and the comment on /TAPECOMM will be ignored. Any spaces must be coded as an underscore. For example: /TAPECOMM=A_backup_tape Check out chapter 4.10 for odds and pieces about tape-support. The way CDZ detects errors on the tape-drive is very rudimentary. If an error occurs, the error will be routed to CDZ and CDZ will report the error. If there is already data obtained from the tape, the database will be updated (even with the error). If there wasn't any data (f.i. when the tape was not mounted), the database will not be updated and the previous status will still apply ! 4.10 Notes on tape support ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ CDZ can access the tape-drive thru the CMS TAPE.EXE utility. Up to now, CDZ could only be tested with release 3.03 of the CMS software (Jumbo version). If you have a different release, you can *try* to use that version, but make sure to create an empty database with CATDISK itself and use that base for testing. I would like to know if other versions work. The same goes for CMS software for other types of tape-drives like parallel drivers and the Tracker <tm>. See HELPTAPE.ME! for more info on this subject ! On one TAPE (DC2000/DC2120), there can be one or more VOLUMES. Each VOLUME can have one or more FILES inside. When you create a backup with TAPE.EXE, CPBACKUP (QIC-40/80 compatible format) or NBACKUP (2.0 or 2.2), one or two VOLUMES are written for every backup (the second could be a copy of the backup-catalog). CDZ will maintain CATDISK COMPATIBLE databases (the SUM and DTA files). They are NOT CATDISK databases but merely databases that are compatible with CATDISK. The initial database (the first, empty database for your tapes) must be created with CATDISK.EXE though ! CDZ will obtain all information about VOLUMES. Normally there is a comment attached to the VOLUME (like FF83950A.FUL, A Norton Backup Catalog or something else). A VOLUME is stored inside a CATDISK <tm> COMPATIBLE database as a file, belonging to the tape (like a file belonging to a diskette). The actual volumes don't have logical names but will be stored as filenames VOL__xxx.TAP (where xxx is the xxxth volume on that TAPE). The description will tell the actual contents of that VOLUME. CDZ will also obtain all information about FILES inside VOLUMES (when you did not supply /NOFILES and the VOLUME is QIC-40/80 compatible and compatible with CMS TAPE.EXE). CDZ will store each FILE inside a tape VOLUME in a CATDISK <tm> COMPATIBLE database as a file (*LBR type) belonging to an archive. The archive is the main-filename (e.g. the tape-volume, e.g. VOL__xxx.TAP) and all files inside the VOLUME will be chained to VOL__xxx.TAP. I have used the *LBR (LU/LIBRARY) attribute inside the CATDISK structure because it is not frequently used but still available (a new attribute for tapes, Rick ??). If the VOLUME seems not to contain files inside, it will probably not be compatible with TAPE.EXE. CDZ does create and update the CATDISK database in a different way as CATDISK <tm> itself does. It is advised to use separate databases for diskettes and tapes. First because they don't mix that well and secondly, when I have made logical errors in the way I maintain the database, you must blame me and not the author of CATDISK. In fact, CDZ creates/updates a DTA/SUM file by itself and the internals of these files happen to be the same as the DTA/SUM files that CATDISK itself maintains. That is why you can use CATDISK to view these files and create reports ! You can also remove entries and do other things with them, like changing the comments ! Again, when you have any problems with CATDISK <tm> and the DTA/SUM files created by me, don't blame the author of CATDISK. Also don't blame me, there is NO guaranty that it works !! In version 2.01 there is NO check that the DTA/SUM files get to big. If they are, they are not anymore compatible with CATDISK but can still be listed with CDF.EXE ! To keep them compatible, I advise you to check for the number of files and volumes on a regular basis. In a next version, I will do the checks myself (when CDZ seems useful to you all). ≥One tip about tape-support and the usage of CATDISK <tm> in general. ≥You *should* install CATDISK in a way that it will extract filenames ≥from archives by default. If you don't want to use this option but you ≥still want to use the CDU tape-support, you should still switch the ≥option to on and supply a run-time option to CATDISK <tm> to switch it ≥off by default (unless you access your tape catalog). If the ≥extraction ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 5 ≥ Version information and credits ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ 5.1 The BETA-team ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ Look into the file SUPPORT.CDU for a full list of all beta-testers. 5.2 Credits ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ Thanks to the following people: - Rick Hillier for CATDISK <tm>; - The BETA-team (a very warm and loud applause !); 5.3 Version history ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 1.xx ≥ Changes ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ˛ All programs compatible with CATDISK 6.3x versions. ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 2.01 ≥ Major Release ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ⁄ƒƒƒƒƒø ≥ CDC ≥ ¿ƒƒƒƒƒŸ ˛ Replaced some buggy routines; ˛ Fixed some coding to make the names of the temporary files more consistent with all other CDU programs; ⁄ƒƒƒƒƒø ≥ CDF ≥ ¿ƒƒƒƒƒŸ ˛ Replaced a routine which could (under rare conditions) cause a hangup; ˛ Fixed a problem with very big file-sizes and disk-sizes which caused CDF to screw-up the screen. Also with CDZ (tape-support) in mind, a longer field would be nice. When the file-size is 10 MB or more, CDF will now display the value in MB; ˛ Fixed some coding to make the names of the temporary files more consistent with all other CDU programs; ⁄ƒƒƒƒƒø ≥ CDM ≥ ¿ƒƒƒƒƒŸ ˛ Replaced a routine which could (under rare conditions) cause a hangup; ˛ Fixed some coding to make the names of the temporary files more consistent with all other CDU programs; ˛ Added the support for the BASEOPTIONS and BASEDRIVE options in the CDx.CTL file (see documentation); ˛ Fixed a problem where CDM would show an empty entry on the list of diskette volumes when there were more files to copy than there was room on all the diskettes; ˛ CDM will now also show the NEXT diskette to mount when the request for the current diskette is displayed; ˛ Added the option to supply the directory, on which CDM has to work on, on the command-line. CDM will still try to match this directory with one of the DIRECTORY2BASE options in CDx.CTL (if any); ⁄ƒƒƒƒƒø ≥ CDR ≥ ¿ƒƒƒƒƒŸ ˛ Replaced a routine which could (under rare conditions) cause a hangup; ˛ Fixed some coding to make the names of the temporary files more consistent with all other CDU programs; ˛ Added the support for the BASEOPTIONS and BASEDRIVE options in the CDx.CTL file (see documentation); ˛ CDR will now also show the NEXT diskette to mount when the request for the current diskette is displayed; ˛ Added the EXCLUDEFILE option to make it possible to exclude one or more files from removal, even when they match the criteria (on date and/or filemask); ⁄ƒƒƒƒƒø ≥ CDS ≥ ¿ƒƒƒƒƒŸ ˛ Replaced a routine which could (under rare conditions) cause a hangup; ˛ Fixed some coding to make the names of the temporary files more consistent with all other CDU programs; ˛ Added the support for the BASEOPTIONS and BASEDRIVE options in the CDx.CTL file (see documentation); ˛ CDS will now also show the NEXT diskette to mount when the request for the current diskette is displayed; ⁄ƒƒƒƒƒø ≥ CDT ≥ ¿ƒƒƒƒƒŸ ˛ Replaced a routine which could (under rare conditions) cause a hangup; ˛ Fixed some coding to make the names of the temporary files more consistent with all other CDU programs; ⁄ƒƒƒƒƒø ≥ CDZ ≥ ¿ƒƒƒƒƒŸ ˛ This program (tape cataloging in a CATDISK <tm> database) is now added to the set of CDU utilities ! ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 2.10 ≥ Minor Release ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ˛ All programs changed to the new CATDISK <tm> 7.00 release. You can NOT use this version with CATDISK 6.3x. Use CDU 2.01 instead when you are still using CATDISK 6.30 to 6.37, better, upgrade to the new CATDISK 7.00 ! ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 2.11 ≥ Bug Fix ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ⁄ƒƒƒƒƒø ≥ CDT ≥ ¿ƒƒƒƒƒŸ ˛ Fixed a problem where CDT could not work with the BASEOPTIONS and BASEDRIVE options in CDU/CDT.CTL ! ⁄ƒƒƒƒƒƒƒ¬ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒø ≥ 3.01 ≥ Major Release ≥ ¿ƒƒƒƒƒƒƒ¡ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒŸ ⁄ƒƒƒƒƒø ≥ CDC ≥ ¿ƒƒƒƒƒŸ ˛ Replaced CDU.CTL into CDU.INI. See CDUTO301.DOC for details about the changed names of the various options and a way to convert your CDx.CTL to CDU.INI in a jiffy; ˛ Changed the behavior of the pick-list. The databases will now be displayed in alphabetical order; ⁄ƒƒƒƒƒø ≥ CDE ≥ ¿ƒƒƒƒƒŸ ˛ CDE is new for this release; ⁄ƒƒƒƒƒø ≥ CDF ≥ ¿ƒƒƒƒƒŸ ˛ Fixed various bugs in the memory support and selection; ˛ Fixed a documentation-bug on the CDF help-screen for the /ARC command-line parameter; ˛ Corrected the trapping of an empty database. When you selected a newly created 0-length CATDISK <tm> database, the screen (and the program) would go wild; ˛ Replaced CDU.CTL into CDU.INI. See CDUTO301.DOC for details about the changed names of the various options and a way to convert your CDx.CTL to CDU.INI in a jiffy; ˛ Changed the behavior of the pick-list. The databases will now be displayed in alphabetical order; ˛ Added a DOS-shell to CDF. You can press <S> to go into a windowed DOS-shell; ˛ Added a <N>ew option so you can change the file-selection and (if you did not include a specific database on the command-line) the name of the database to view at; ˛ Added the option to disallow the usage of XMS or EMS with the UseEMS and/or UseXMS option (default set to TRUE); ⁄ƒƒƒƒƒø ≥ CDM ≥ ¿ƒƒƒƒƒŸ ˛ Fixed some bugs that occurred when running CDM with an alternate directory (not being the current directory). Deletion of files (duplicates) would not occur, also sometimes a file would be ignored; ˛ Replaced CDU.CTL into CDU.INI. See CDUTO301.DOC for details about the changed names of the various options and a way to convert your CDx.CTL to CDU.INI in a jiffy; ˛ Changed the behavior of the pick-list. The databases will now be displayed in alphabetical order; ˛ Added file-comments. CDM will now look for FILES.BBS, DESCRIPT.ION or a ????????.I?? DISP-compatible comment-file that came from FileDoor <tm> (and duplicated by many others). If the file is present in one or more of these files, the comment for that file (if present) will be displayed at the bottom of the screen. If there is NO comment, NO display of comments will occur ! ˛ On general request, I have included the file-extension in the CDM displays. For version-control and duplicate checks, CDM will NOT look at the extension ! ˛ Added help on all keyboard-input. If you press 'H' (on any of the questions inside CDM, not the picklist), you will get some extra help about the choices you can make; ˛ Added a DOS-shell (press <S> at any keyboard-input except the pick-list). The DOS-shell is a swapped (full memory) and windowed shell. If you screw-up the display (f.i. when you 'LIST' a file or other programs that write directly to the screen), CDM will restore it on EXIT; ˛ Expanded the old CDM fill-algorithm. While this is still under development, the current algorithm should work much better than the previous ones in earlier versions. A tradeoff is, that you now have to answer all unusual questions first (version control, duplicates), before CDM asks to add (or not add) the file to the set of diskettes. With this algorithm, the filling of the diskettes will be from start to finish and will not be as random as before. This is causes mainly because CDM will now first calculate the space that will be released by deleted files or newer versions, before the new files are added; ˛ Added a new option EXCLUDEFORPROCESSING in CDU.INI. This option can be used to exclude one or more files (mask) from processing by CDM. A question for these files will never be asked and the files will always stay in the directory; ˛ Added a new option TRIGGERCDTONFILE in CDU.INI. This option can be used to mask one or more files that will cause CDT to be called from within CDF. These files MUST be excluded with the previous options, because they would otherwise be gone before CDT would trigger. Some examples are FILES.BBS, DESCRIPT.ION and the *.I?? FileDoor <tm> compatible comment-files. For EVERY match, CDT is called. CDT will add the comments to the database(s) provided that you included options for CDT that can be used with the triggered files; ˛ Added a new option CDTPROGRAMPATH in CDU.INI. If you use the TRIGGERCDTONFILE option, this option can be used to point to the name and location of CDT.EXE if it can not be found in the search-path; ˛ Added the option to disallow the usage of XMS or EMS with the UseEMS and/or UseXMS option (default set to TRUE). These options will be taken into account when swapping the programfrom memory; ˛ Added the option to supply a file-mask, so CDM will only catalog the file(s) (also move) that match this wildcard. You can combine the filemask with a directory; ˛ Added a routine that will remove any entry from FILES.BBS in the directory that contained the original file, providing FILES.BBS it not moved to diskette as well. CDM will update FILES.BBS AFTER any call to CDT, so there is still the option to copy the comment from the original FILES.BBS to the CATDISK <tm> database; ⁄ƒƒƒƒƒø ≥ CDR ≥ ¿ƒƒƒƒƒŸ ˛ Fixed a problem in the file-selection. If a file (without its extension) would be less than 8 characters, it would sometimes not match the supplied wildcard; ˛ Fixed a problem where CDR would also include in-archive files for the selection; ˛ Replaced CDU.CTL into CDU.INI. See CDUTO301.DOC for details about the changed names of the various options and a way to convert your CDx.CTL to CDU.INI in a jiffy; ˛ Changed the behavior of the pick-list. The databases will now be displayed in alphabetical order; ˛ Added help on all keyboard-input. If you press 'H' (on any of the questions inside CDM, not the picklist), you will get some extra help about the choices you can make; ˛ Added a DOS-shell (press <S> at any keyboard-input except the pick-list). The DOS-shell is a swapped (full memory) and windowed shell. If you screw-up the display (f.i. when you 'LIST' a file or other programs that write directly to the screen), CDM will restore it on EXIT; ˛ Added the display of the file-comment (when available inside the current CATDISK <tm> database. If no comment is set, no comment is displayed at the bottom of the screen; ˛ Added the option to disallow the usage of XMS or EMS with the UseEMS and/or UseXMS option (default set to TRUE). These options will be taken into account when swapping the programfrom memory; ⁄ƒƒƒƒƒø ≥ CDS ≥ ¿ƒƒƒƒƒŸ ˛ Replaced CDU.CTL into CDU.INI. See CDUTO301.DOC for details about the changed names of the various options and a way to convert your CDx.CTL to CDU.INI in a jiffy; ˛ Changed the behavior of the pick-list. The databases will now be displayed in alphabetical order; ˛ Added help on all keyboard-input. If you press 'H' (on any of the questions inside CDM, not the picklist), you will get some extra help about the choices you can make; ˛ Added a DOS-shell (press <S> at any keyboard-input except the pick-list). The DOS-shell is a swapped (full memory) and windowed shell. If you screw-up the display (f.i. when you 'LIST' a file or other programs that write directly to the screen), CDM will restore it on EXIT; ˛ Added the display of the file-comment (when available inside the current CATDISK <tm> database. If no comment is set, no comment is displayed at the bottom of the screen; ˛ Added the option to disallow the usage of XMS or EMS with the UseEMS and/or UseXMS option (default set to TRUE). These options will be taken into account when swapping the programfrom memory; ⁄ƒƒƒƒƒø ≥ CDT ≥ ¿ƒƒƒƒƒŸ ˛ Replaced CDU.CTL into CDU.INI. See CDUTO301.DOC for details about the changed names of the various options and a way to convert your CDx.CTL to CDU.INI in a jiffy; ˛ Added special code for DESCRIPT.ION files. If they are present and you have supplied entries for them in CDU.INI, CDT will convert the file to a temporary file that can (and will) be imported by CATDISK. This temporary file will start on position 1 (over a length of 12 bytes) for the filename and position 14 for comments; ˛ Added the option to disallow the usage of XMS or EMS with the UseEMS and/or UseXMS option (default set to TRUE). These options will be taken into account when swapping the programfrom memory; ⁄ƒƒƒƒƒø ≥ CDZ ≥ ¿ƒƒƒƒƒŸ ˛ Replaced CDU.CTL into CDU.INI. See CDUTO301.DOC for details about the changed names of the various options and a way to convert your CDx.CTL to CDU.INI in a jiffy; ˛ Changed the behavior of the pick-list. The databases will now be displayed in alphabetical order; ˛ Added the option to disallow the usage of XMS or EMS with the UseEMS and/or UseXMS option (default set to TRUE). These options will be taken into account when swapping the programfrom memory; 5.4 Copyright, Trademarks ƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒƒ CATDISK is a trademark of Rick Hillier NBackup, NDOS and Norton are trademarks of Symanec Coorporation CPBackup is a trademark of Central Point Software Inc. 4Dos is a trademark of J.P. Software / R.C. Conn and T. Rawson Stacker is a trademark of Stac Electronics, Carlsbad Diet is a trademark of Teddy Matsumoto Doublespace is a trademark of Microsoft CMS, Jumbo and Tracker are trademarks of Colorado Memory Systems CDU is written in Borland Pascal 7.0, with help of the Turbo Debugger 3.0 and makes extensive use of Object Professional 1.20. Borland Pascal is a trademark of Borland International Turbo Debugger is a trademark of Borland International Object Professional is a trademark of TurboPower Inc. ==================== END OF DOCUMENT ==================================